@tysonclugg We're thinking of removing pubsub from the js-libp2p monorepo (in the future perhaps as a part of v3) and so, this PR is better served to be made against https://github.com/ChainSafe/js-libp2p-gossipsub
@achingbrain will create an issue in that repo describing the current state of wonky interfaces between pubsub and gossipsub in that repo as well

I'm of the opinion that js-libp2p-gossipsub should be merging into js-libp2p instead of the other way around.

In the interim (until things are moved one way or the other), this is still the correct place for this PR. There is no other place to submit this code change which has clear benefits for the typing system. I would very much appreciate this being merged now, and not put off because of a potential future change in policy (which hasn't been announced anywhere at this stage that I can see).

Q1: @achingbrain What assurances do we have that anything is being done in the ChainSafe repo? Are PRs such as #523 being looked at, and are ChainSafe still actively developing js-libp2p-gossipsub for use with their own active projects?

Q2: @p-shahi What assurances do we have that PubSub will remain as a level 3A (recommended active) part of libp2p, and isn't destined for deprecation?

My concerns about moving PubSub out of libp2p is that it will rapidly degenerate into disrepair, thereby forcing a negative response to Q2 above. Moving gossipsub into libp2p helps to keep things from going stale and overall should improve the situation (eg: PR 523 linked above).